Cream of the Crop 1

home *** CD-ROM | disk | FTP | other *** search

/ Cream of the Crop 1 / Cream of the Crop 1.iso / UTILITY / EVENT21.ARJ / EVENT.DOC next >

Wrap

Text File | 1991-01-10 | 42KB | 693 lines

┌──────────────────────────────────────────────────────────────────────────────┐ │ ┌──────┐ ┌─┐ ┌─┐ ┌──────┐ ┌───┐ ┌─┐ ┌───────┐ │ │ │ ┌───┘ │ │ │ │ │ ┌───┘ │ ┌┐└┐ │ │ └──┐ ┌──┘ │ │ │ └─┐ │ │ │ │ │ └─┐ │ │└┐└┐│ │ │ │ │ │ │ ┌─┘ │ │ │ │ │ ┌─┘ │ │ └┐└┘ │ │ │ │ │ │ │ └┐└─┘┌┘ │ │ │ │ └┐ │ │ │ │ │ │ └───┐ └┐ ┌┘ │ └───┐ │ │ └┐ │ │ │ │ │ └──────┘ └─┘ └──────┘ └─┘ └─┘ └─┘ │ │ ┌────────┐ ┌─┐ │ │ └──────┐ │ │ │ │ │ │ │ │ │ │ │ ┌──────┘ │ │ │ │ │ │ ┌──────┘ │ │ │ │ │ │ │ │ │ │ │ └──────┐ ┌┐ │ │ │ │ └────────┘ └┘ └─┘ │ │ │ │ EVENT -- The DOS Scheduler Ver 2.1 │ │ │ │ EVENT(C). John Wagner 1990,91. All rights reserved │ │ │ └──────────────────────────────────────────────────────────────────────────────┘ For information on what is new for Ver 2.1, see the text file WHATS.NEW. (R)=Registered Users Only (U)=Un-Registered Users Only Legal Mumbo-Jumbo: ┌──────────────────────────────────────────────────────────────────────────────┐ │ For the sake of argument, the EVENT.EXE, UP_DATE.EXE, REG.KEY, UNREG.KEY and │ │ EVENT.DOC may (and will) be referred to by the terms: EVENT, the program, │ │ the software. │ │ │ │ I, John M. Wagner retain ALL rights to distribute and collect fees for this │ │ software. This software IS NOT RELEASED TO THE PUBLIC DOMAIN!!! IT IS NOT │ │ FREE!!! It is OWNED by me and only me! │ │ You, as a user have the right to possess and distribute this software. You │ │ MAY NOT collect ANY FEE, real or otherwise for the transfer of this │ │ software, Exception: You may charge the cost of distribution (ie: phone │ │ transfer costs, floppy disk/mailers, postage. It is to be understood, with │ │ the party that is charged these fees, that paying transfer costs DOES NOT │ │ constitute a registration fee to the author and that a registration fee is │ │ STILL required after evaluating the software. │ │ │ │ DISCLAIMER NOTICE: │ │ This program was written by John Wagner. I, John Wagner accept │ │ NO RESPONSIBILITY for ANY damages, real or otherwise that this program │ │ or any programs that it runs may cause. I make no guarantees that this │ │ program works as described in this document file or anywhere else. This │ │ software is provided "AS IS" with NO GUARANTEE, expressed or implied. │ │ USE IT AT YOUR OWN RISK! │ └──────────────────────────────────────────────────────────────────────────────┘ User Supported Software: (U)This program is being distributed as "User-Supported Software". What does this mean? This means that you may TRY the program before you BUY it. This DOES NOT mean this software is free. You can see the program run and evaluate its use to you, before you pay for it. (U)Often the question arises as to what constitutes "TRYING" a program. For the purpose of THIS SOFTWARE, TRYING means that you may use the program 10 TIMES. After you use the software 10 TIMES, you will know if you want to continue using the program or not. If you don't want to use the program anymore, delete all copies you have of the software and discontinue USING it. If you decide to keep using the program you must send in your registration fee. (U)Registering EVENT: Registration is $20 per copy, for the first 5 copies. Additional copies after the initial 5 are $5 per copy. A site license is negotiable. Payment is accepted by check (allow 4 to 6 weeks to clear) or money order only. NY state residents must add 7% sales tax. Make all checks and money orders payable to: John Wagner. Specify 360k or 1.44 meg (add 1 dollar for 1.44) format. (If you don't I will send you 360k) Update by Mail Plan: For an additional $7 per copy, I will send you the next 5 releases of the program as they become available ($12 per copy for 1.44 meg). You may apply this plan to as many (or as few) copies as you wish. HOW TO ORDER: ┌──────────────────────────────────────────────────────────────────────────────┐ │ Include the following information in your order: │ │ How many copies? │ │ Disk format? │ │ Shipping address? │ │ Amount enclosed? │ │ Update by mail plan? │ │ Special Requests? │ │ │ │ Mail your order and payment to: John Wagner │ │ RR1 157 Box M │ │ Taberg, NY 13471 │ │ │ │ Order MUST INCLUDE payment in FULL, NO COD's. Money orders and Checks │ │ ONLY. Do not send cash. │ │ │ └──────────────────────────────────────────────────────────────────────────────┘ (U)Within 2 to 4 weeks you will receive your disk(s) with the latest version of EVENT and a personalized REG.KEY file. If later versions of the software are released, they will be posted on KADET BBS (see end of DOC file). You can simply call KADET and download the latest version, and use your REG.KEY file with the new program. What this means in laymens terms is: ONCE A REGISTERED USER, ALWAYS A REGISTERED USER! You have received the latest version of the EVENT program on this disk. (R)You have also received your own personalized "REG.KEY" file. (R)Please do not distribute your "REG.KEY" file. Doing so would violate the terms of your license and violate the copyright I have on the program. (U,R)WARNING!: DO NOT MODIFY THE REG.KEY FILE IN ANY WAY! Doing so might (read: most probably will) make the file useless. If it's your only copy, your out of luck! I hereby give permission for you to make 2 copies of the "REG.KEY" file. 1 for back up and 1 for archival purposes. What is EVENT?: EVENT is a simple to use, but very powerful program. EVENT allows up to twelve different system events to be pre-programmed and processed at specified times. You may also chain event files together to allow an infinite number of events to be pre-programmed. Why is EVENT?: I wrote this program for me. To increase the life of your hardware, it is now recommended that you leave your system on at all times. This is to prevent the wear and tear from turning your system on and off. So, all the time my system is running unattended, it should be doing some work! It would be a real waste to have it just sit there. Henceforth: EVENT. Why should I waste MY time just watching my computer while it does things like run a comm program with a script file that gets my mail. Optimizing a hard disk is great, but not a very interactive process and I don't feel I need to watch it! There are many reasons for running this program. Even if you don't use it all the time (I do), there will be a lot of times when it will come in handy. What can it do? I think it would be better put: What cant it do! I have yet to find a program that cannot be run under EVENT. If your program requires you to physically enter key strokes, this can USUALLY be overcome using DOS's indirection operators. A full explanation of indirection and DOS is not in the scope of this DOC, if need information on these subjects, consult your DOS manual. The uses of this program are endless: E-Mail transfers, system backups and other daily events are just a minute inkling of what you can pre-set your computer to do. If a program can be run from a batch file, it can be run from EVENT. Run time consuming programs, programs that require you to just sit there and watch, disk compression programs, compile large files, WHATEVER! You could set up your system to call a distant Bulletin Board Service (BBS) to transfer mail during the reduced phone rate time periods. The savings will start to show immediately. Backup critical system files during the night. After everyone has gone home from work, let the computer keep on working! Going on a trip? Use this program to bring up your communications software at specified times so that it can receive your call. With a little imagination this program can become one of your most valuable tools. Use the CHAIN_EVENTS and UP_DATE features and program your system for years in advance! I've let my system run on it's own and collect mail for me for the past four months. Using this program increases productivity. It allows you more time to do actual work, and that is the bottom line. Power Outage?: EVENT automatically tracks what it has done up to the time the program was shut off. Use the AUTO RECOVER feature to bring up EVENT and continue where it left off in the event of a power outage. The EVENT program keeps a log of what was accomplished in a file with the same name as your EVENT file except with the extension .LOG. To view the .LOG file, use the built in LOG file viewer. See the section near the end of this DOC file called: "Recovering from a power outage:" for more information on recovering from a power outage while running EVENT. Use EVENT with DESQview: The DESQview environment is ideal for EVENT. Run the program in the background while you are still working! EVENT allows large programs to run: When EVENT shells out to run a program, it can be configured to load itself into Extended memory or Expanded memory or a Disk Drive. This swapping is optional and configurable and is highly desirable. When it swaps out, EVENT uses 6K of RAM, the rest is free to run the program the EVENT calls. SWAP FILES: If your configuration allows for swapping and EVENT finds no XMS or EMS to swap itself out to, it will try to use a swap file on disk. Where EVENT places it's SWAP FILE is up to you. You specify the SWAP FILE drive/directory in your EVENT.CFG file. If none is specified in your EVENT.CFG file, it will use the root directory of the disk drive the program is running on. The SWAP FILE will be hidden. The SWAP FILE will be erased as soon as the program returns from it's shell. The SWAP FILE is about 133K long so be sure there will be space on the drive/directory you specify. Also be sure the drive you specify is not write protected. (IMPORTANT!) System Configuration: IMPORTANT!!! ┌──────────────────────────────────────────────────────────────────────────────┐ │ Make a sub-directory called EVENT. Copy all the files on this disk into │ │ the directory you created. │ │ │ │ Use your Hard Drive: │ │ EVENT may be run from a floppy but I don't recommend it. The COMSPEC │ │ variable is used to locate a copy of COMMAND.COM to invoke a shell when │ │ running an EVENT or using an external editor or using the DOS-SHELL. If you │ │ run off a floppy and EVENT can not locate COMMAND.COM, the operation will │ │ fail. It can also be configured to place it's swap file on a floppy, but │ │ again, I don't recommend it. It's not harmful, it's slow. │ │ │ │ There is a section at the end of this DOC file containing RECOMMENDED setups │ │ for all system configurations. │ └──────────────────────────────────────────────────────────────────────────────┘ ┌──────────────────────────┐ │ HOW DO I RUN THIS THING? │ └──────────────────────────┘ Running the program: From the DOS command line, the programs usage is as follows: ┌───────────────────────────────────────────┐ │ USAGE: │ │ EVENT │ │ -or- EVENT n │ │ │ │ WHERE: n = filename of EVENT file to run. │ └───────────────────────────────────────────┘ Menuing System: The menu system is a standard pull down menu interface. Use the arrow keys to move the selection bar (RED) to the option you want and press Return. If you have a mouse you may use it to point at the option you want and click on it (point and shoot) with the Left Mouse Button (LMB). To close a pull down menu press the Escape key or click the Right Mouse Button (RMB). Pickfile Window: When given the option of entering a filename (.EVT or .BAT), pressing Alt-D will bring up a "Pickfile Window" with all the existing files in the current directory with the matching extension for the operation (*.BAT or *.BAT). The window will also have all sub-directories in it. If there are no files that match the search criteria the Pickfile window will automatically return to the text entering function. Use the arrow keys, Page Up, Page Down, Home or End keys to move the selection bar (RED) to the file you wish to load and press the Enter key. If you select a sub-directory, the program will change to the directory you selected and the process will start all over again until you either pick a file or press the Escape (Esc) key or click the mouse on the Close Box. After a file is selected, it's name will be shown on the edit line just as if you typed it in. Pressing Enter again will bring up the proper editor for the operation. If you are using a mouse, point and shoot (LMB) at the filename/sub-directory you wish to select. The RMB is the same as pressing the Escape key. Sample Pick File Window: Title Bar displays filespec Close Box ──────┬──────────────────── ────┬──── │ │ ┌────┬─────────────────────────────────────────────┐ └───│ ── │ C:\EVENT\*.EVT │ ├────┴─────────────────────────────────────────────┤ │ . .. TEST.EVT NEW.EVT │ │ │ │ MORNING.EVT EVENING.EVT COMPRES.EVT │ │ │ │ │ └──────────────────────────────────────────────────┘ Mouse Users: The mouse is fully supported in EVENT. In menu operations it functions as a "Point and Shoot" device and during editor (internal) operations, rolling the mouse is the same as using the arrow keys. The LMB is functionally the same as the Enter key and the RMB is functionally the same as the Escape key. The following options are available from the Main Menu: INFO, FILE, OS-SHELL or EXIT INFO gives a quick overview of the program. FILE gives you the option of either, Loading an EVENT File, Editing the EVENT File in Memory, Running the EVENT File in Memory, Using the Batch file editor or editing (or creating) the Configuration file (EVENT.CFG). Loading an EVENT File: Editing an EVENT file: After loading an EVENT file, you will be placed in the EVENT editor. If you have an EVENT already loaded and select EDIT from the Main Menu you will use the same editor. Table 1.1 outlines the editors commands. Table 1.1: ┌──────────────────────────────────────────────────────────────────────────────┐ │ │ │ Key Action │ │ --- ------ │ │ LeftArrow cursor left │ │ RightArrow cursor right │ │ UpArrow cursor up │ │ DownArrow cursor down │ │ Ctrl-LeftArrow word left │ │ Ctrl-RightArrow word right │ │ Tab field right │ │ Shift-Tab field left │ │ Enter process field │ │ Ctrl-Enter process all fields │ │ Home beginning of field │ │ End end of field line / end of field │ │ Ctrl-Home beginning of first field │ │ Ctrl-End end of last field │ │ Ins toggle field insert mode │ │ Del delete character at cursor │ │ BackSpace delete character left │ │ Ctrl-BackSpace delete word left │ │ Ctrl-R restore field to original contents │ │ Ctrl-T delete word right │ │ Ctrl-U delete to end of field │ │ Ctrl-Y delete to end of last field │ │ Esc abort data entry │ └──────────────────────────────────────────────────────────────────────────────┘ DATE: Enter the date in the format MM/DD/YY. If you want to automatically enter the system date, move the cursor to the first column (left most) of the date field and press ALT-D. TIME: Enter the Time in military (24 hour) time format: (e.g., 23:00. would equal 11 p.m.) If you want the EVENT to execute immediately, don't enter a time. EVENT: Enter the Event you want to run. Enter it just as you would on the DOS command line. If your event includes more than one command, write a batch file to include all of the commands and specify the name of the batch file on the Event line. EVENT will search the PATH environment variable to find a program. If the program you want to run resides in a directory other than the directory EVENT is in, you may specify it's path or write a batch file that changes to the correct directory/drive to run the program if it doesn't reside in a directory specified by your PATH statement. EVENT switches back to the directory/drive that the EVENT program was started from so changing the directory as one EVENT and running the program as another will not work. Always make sure the program you run exits to DOS when it is finished. Chaining Events: This program can also be used to load a subsequent event(s) file. To have it do so, enter the command "CHAIN_EVENTS" and the name (no extension needed) of the subsequent event file. For example, to discontinue the event that is currently loaded and start processing another event called DATABACK which (must be created before you try to run it!), type "CHAIN_EVENTS DATABACK" in the event field. IMPORTANT: After EVENT reaches a CHAIN_EVENTS event, the calling event file will be closed and any events programmed after the CHAIN_EVENTS command will not be processed. If you wish to chain more event files, you must call CHAIN_EVENTS from the file you just chained to. UP_DATE: UP_DATE.EXE provides an alternative to writing a different EVENT file for EVENTS that will be run as daily events. With UP_DATE you can run the same EVENT for many days (or years) without having to re-edit it or CHAIN_EVENTS to an EVENT file that only changes the date. UP_DATE.EXE: ┌────────────────────────────────────────────────┐ │ USAGE: UP_DATE n │ │ │ │ WHERE: n = name of EVENT file to update. │ └────────────────────────────────────────────────┘ UP_DATE will increment the date field in the event file specified by 1. If UP_DATE is run on the current EVENT file, the changes will not take effect until the EVENT is reloaded with CHAIN_EVENTS. Leap Year? Not to worry, I remembered to put it in! Example event file called BACKER.EVT: ┌──────────────────────────────────────────────────┐ │DATE TIME EVENT │ │10/02/90 10:10 COPY D:\WKS\*.WKS A: │ │10/02/90 12:00 C:\COMM\QMODEM\MAILRUN.BAT │ │10/02/90 12:10 COPY C:\XFER\*.QWK D:\MAIL │ │10/02/90 13:05 UP_DATE BACKER │ Increment dates │10/02/90 13:10 CHAIN_EVENTS BACKER │ Reload EVENT with new dates │ │ │ If the date field is blank, you │ │ may use the EVENT field to put │ │ in comments. │ │ │ └──────────────────────────────────────────────────┘ When you are through editing your EVENT file, press Ctrl + Enter, the file will be saved to disk. To abort the entries press ESC. Running an Event: After either creating or loading an Event file, you are ready to RUN! Select this option and let the program do the rest! The program will run even after the last event was processed. Pressing the ESC key during the EVENT processing will stop the EVENT and display a report of what has been done prior to halting. Pressing the space bar will toggle the screen display on and off. Batch file editor: The batch file editor included in this program is very simple and NOT designed nor intended for serious programming use. It is included as an extra tool for batch programming and is very limited in capabilities. Only 23 lines of 80 characters per line are allowed. As an alternative to the internal batch file editor, you may specify an external editor to use when this option is selected. See the section on Configuration for setting up an External Editor. Select Batch Editor from the FILE menu. If any BATCH files (*.BAT) exist or you are in a sub-directory you will see a pickfile window. Otherwise you will be prompted to enter a filename. Enter the name you want to give the BATCH File (or the name of an existing BATCH file) or press Alt-D to bring up a pickfile window or hit the ESC key to abandon this operation. After selecting a file, either from the pickfile window or typing one in, press the ENTER key. If the filename you specify does not exist, you will be asked if you want to create it. You may enter an extension, but the program will automatically substitute it with a .BAT extension. Configuration File: EVENT saves it's configuration by modifying EVENT.EXE with parameters you supply. If you use a program such as PKLITE, or LZEXE to compress the EVENT.EXE file, and then try to alter the programs configuration, an error will occur. Always alter the configuration on a fully expanded version of the program, and then compress it when you are satisfied with the configuration. Here are the Configuration options: Path to External Editor: Enter in the drive/path that your external editor resides on/in. If don't have one or don't want to use one, just leave the field blank. Example: To use the QEDIT editor in the C:\EDIT directory, enter: C:\EDIT\Q Path to SWAP directory: Enter in the drive/path that you want EVENT to place it's SWAP FILE if it is needed. If you leave the field blank, the program will use your root directory. Don't despair, the SWAP FILE gets erased when the program is done using it! Example: To use the C:\WINDOWS\TEMP directory, enter: C:\WINDOWS\TEMP Allow swap when using editor: Allow swap when running EVENT: Allow swap when in DOS SHELL: These are all yes (Y) or no (N) answers. What this means is do you want the program to swap itself out XMS, EMS or disk when shelling during the operation specified. I recommend answering yes (Y) to all of the above to allow the program you are going to run as much memory as possible while it is running. You might have a very valid reason not to do this so the option is yours. Use External Editor: If no external editor is specified or for some reason you do not want to use your external editor select no (N). Otherwise select yes (Y) to use the external editor while editing batch files. Log Viewer: Use this to view the files with a .LOG extension that are created by the program when an EVENT is run. The .LOG file will contain a list of what was done and the start and stop times. OS-SHELL gives you a shell to DOS. Type EXIT to return to the program. EXIT quits the program and exits you to DOS. Recovering from a power outage: This is one of EVENT's most powerful features. The program tracks what EVENT's have not been run yet by keeping a spare EVENT file on disk called CURRENT.EVT. The CURRENT.EVT file is a standard .EVT file, that the program updates each time, after it runs an EVENT. It is identical to the EVENT file that the program is processing EXCEPT it rewrites itself after every EVENT is run, deleting the EVENT that was just run after it is done. If there is a power outage, your system will re-boot. If you place the following lines at the end of your AUTOEXEC.BAT file, you can restart EVENT where it left off when the power went out and continue processing! Here is what you need to add to your AUTOEXEC.BAT file: REM Change drives and directories to the REM drive/directory EVENT resides on. C: cd\event EVENT CURRENT.EVT REM Your system configuration will probably REM differ, so use your configuration, REM not mine! This will start up EVENT and load CURRENT.EVT for immediate execution. CURRENT.EVT will have all the EVENTS that did not get run from the EVENT file that was running when the power went out or the system re-booted. The .LOG file will be changed from the filename of the EVENT file that was running to CURRENT.LOG. The first .LOG file will still be there for you to examine. .LOG files: EVENT creates a file called a .LOG file whenever it runs an EVENT. The .LOG file will have the same filename as the .EVT file you are running but it will have a .LOG extension. If you use the CHAIN_EVENTS feature, the .LOG filename will NOT change to the .EVT filename that was chained to. It will retain the filename of the "parent" .EVT file. EXCEPTION: During a power failure when the CURRENT.EVT file is run, CURRENT.LOG will become the current .LOG file but the "parent" .LOG file will still be there for examination. Common Problems and Questions: ┌──────────────────────────────────────────────────────────────────────────────┐ │ │ │ Question: │ │ This "SWAP FILE", swap when using whatever stuff is confusing. Please │ │ recommend a good setup. │ │ Answer: │ │ For a standard Hard Disk setup, I recommend all swaps be allowed, an external│ │ editor be setup and a temporary directory be set up. I recommend QEDIT for an│ │ external editor and the drive/directory that the .EVT files reside in be used│ │ for the SWAP FILE. │ │ │ │ Question: │ │ Every time I try to run an EVENT or use my external editor or the DOS-SHELL, │ │ the operation fails or I get error messages. │ │ │ │ Answer: │ │ EVENT needs to locate a copy of COMMAND.COM in order to run the external │ │ editor, DOS-SHELL and EVENTS. If your COMSPEC environment variable is set │ │ to a floppy in drive A: and you removed the disk, the program will be │ │ unable to run properly. Follow the guidelines below for floppy setup. │ │ ┌────────────────────────────────────────────────────────────────────────┐ │ │ │ Single floppy setup: │ │ │ │ │ │ │ │ Contents of drive A: COMMAND.COM │ │ │ │ EVENT.EXE │ │ │ │ EVENT.CFG │ │ │ │ REG.KEY (or UNREG.KEY) │ │ │ │ Any .EVT files and batch files you need to run │ │ │ │ │ │ │ │ Set up your EVENT.CFG file as follows: │ │ │ │ ┌───────────────────────────────────────────────┐ │ │ │ │ │ Path to External Editor: │ Leave Blank │ │ │ │ │ Path to SWAP directory: │ Leave Blank │ │ │ │ │ Allow swap when using editor: N │ │ │ │ │ │ Allow swap when running EVENT: N │ │ │ │ │ │ Allow swap when in DOS SHELL: N │ │ │ │ │ │ Use External Editor: N │ │ │ │ │ └───────────────────────────────────────────────┘ │ │ │ │ You may allow swaps if you have at least 133K of XMS or EMS. │ │ │ │ │ │ │ └────────────────────────────────────────────────────────────────────────┘ │ │ ┌────────────────────────────────────────────────────────────────────────┐ │ │ │ Dual Floppy Setup: │ │ │ │ │ │ │ │ Contents of drive A: COMMAND.COM │ │ │ │ Contents of drive B: EVENT.EXE │ │ │ │ EVENT.CFG │ │ │ │ REG.KEY (or UNREG.KEY) │ │ │ │ Any .EVT files and batch files you need to run │ │ │ │ │ │ │ │ Set up your EVENT.CFG file as follows: │ │ │ │ ┌───────────────────────────────────────────────┐ │ │ │ │ │ Path to External Editor: │ Leave Blank │ │ │ │ │ Path to SWAP directory: A:\ │ Leave Blank │ │ │ │ │ Allow swap when using editor: N │ │ │ │ │ │ Allow swap when running EVENT: Y │ │ │ │ │ │ Allow swap when in DOS SHELL: Y │ │ │ │ │ │ Use External Editor: N │ │ │ │ │ └───────────────────────────────────────────────┘ │ │ │ │ NOTE: Depending on the size of your A: drive, you could have an │ │ │ │ external text editor on it and specify it in your EVENT.CFG file. │ │ │ │ EVENT requires about 133K of free disk space to use for a SWAP FILE │ │ │ │ if no XMS or EMS is available. │ │ │ └────────────────────────────────────────────────────────────────────────┘ │ │ │ │ Question: │ │ Can I keep working while EVENT is running? │ │ Answer: │ │ DOS is NOT a multi-tasking operating system so the apparent answer is NO. │ │ HOWEVER, combine EVENT with a DOS multitasker like DESQview or Windows │ │ and the answer becomes, YES, YES, YES. I must say that EVENT runs better │ │ under DESQview then Windows, (I think DESQview is a better program anyway) │ │ but it does run under either. │ │ │ │ Question: │ │ Is EVENT a Terminate Stay Resident (TSR) Program? │ │ Answer: │ │ Not in the truest sense. EVENT does terminate and stay resident when │ │ running a DOS-SHELL, External Editor and EVENT's but it does so │ │ differently from a true TSR. It invokes a secondary command processor, │ │ it does not leave itself in memory after exiting the program. │ │ │ │ Question: │ │ Is it safe to run a program like PC-TOOLS COMPRESS or Nortons SPEED DISK? │ │ Answer: │ │ Yes! │ │ │ │ EVENT is not infalable, it can be crashed. Using some common sense however │ │ will prevent this from happening to you. Below is a list of things NOT TO │ │ DO! │ │ │ │ DO NOT run Terminate Stay Resident Programs from under an EVENT or from the │ │ DOS-SHELL. Doing so WILL cause the program to crash. │ │ │ │ Use caution running more than one copy of the program at a time under │ │ a DOS multitasker. Doing so might (will) erase the other copies SWAP FILE, │ │ CURRENT.EVT and .LOG files (if it is the same). A work around for this would │ │ be to change the second (and every copy after it) programs swap directory to │ │ something other than the first copies. If you are going to attempt this, I │ │ suggest using two entirely different copies of the program in separate │ │ directories with separate EVENT.CFG files that have differing swap file │ │ directories. │ │ │ │ DO NOT run a program that re-boots the computer, doing so would keep │ │ EVENT from re-loading itself. It would also leave a HIDDEN SWAP FILE on the │ │ Hard Disk if one was used. This is not that bad as the SWAP FILE would be │ │ erased the next time the program is run. │ │ │ │ DO NOT run EVENT from a write-protected disk. To do so would cause errors │ │ when saving files and attempting to write the EVENT.LOG and CURRENT.EVT │ │ files while running an EVENT. │ │ │ │ Every attempt has been made to ensure smooth operation. Use your head, the │ │ EVENT program is not infalable, with a little imagination, it can be │ │ crashed. Then again, so can just about any program! │ └──────────────────────────────────────────────────────────────────────────────┘ MegaMail is a Trademark and Copyright of Kip Compton. Qmodem is a Copyright of the Forbin Project. QEDIT is a Copyright of SemWare. DESQview is a Copyright of Quarterdeck. Windows is a Copyright and Trademark of Microsoft. None of the programs is in any way associated with EVENT or John Wagner. A sample BATCH file that will get (call) KADET.BBS and xfer my MegaMail. Comments follow the semicolon ";" and shouldn't be entered. cd\mega ;Change to the ;MegaMail directory if exist c:\xfer\kadet.dl megaread /IMPORT KADET ;Check if there is a ;kadet.dl mail packet. ;If yes, import it. megaread /EXPORT KADET ;Export all new mail ;to KADET BBS cd\comm\qmodem ;Change to the Qmodem ;directory qmodem /S=KADET.SCR ;Start up Qmodem and ;execute the KADET script. ;KADET.SCR will call Kadet ;and open the MegaMail ;door and xfer mail and ;then exit to DOS when ;it's done. cd\mega ;Change to the ;MegaMail directory. if exist c:\xfer\kadet.dl megaread /IMPORT KADET ;Check if there is a ;kadet.dl mail packet. ;If yes, import it. Thats all there is to it! If you can write a batch file to run a task, and the task exits to DOS when done, it can be automated with EVENT. After all, computers were meant to do work FOR us! Let it do it while we are not here! Every attempt has been made to ensure bug-free operation of this program. If you have a problem or a Critter-Report, please contact me at the address below. Ways to contact John Wagner: By Modem: Kadet BBS, Camden NY. (315)245-3815,(DS)8N1. Leave a message in Conference 0 and I'll get back to you within 24-48 hours. US MAIL: John Wagner RR1 157 Box M Taberg, NY 13471 EVENT(C). John Wagner 1990,91. All rights reserved